Yieldbot adapter use utils.timestamp #2848
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description of change
This change refactors the Yieldbot adapter to use
utils.timestamp()
for milliseconds past epoch timestamp values; andutils.timestamp()
implementation is used in place i.e.new Date().getTime()
.Other information
It came to light that certain publishers using the Prebid.js 1.0 Yieldbot adapter have code that redefines
Date.now()
, which prior to this change, the Yieldbot adapter used to obtain timestamp values; therefore, one might consider this a:The publisher code redefined
Date.now()
(among other functions) as follows: